-
Notifications
You must be signed in to change notification settings - Fork 7
Add configurable read/update benchmark with watch support #207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Add read_update benchmark command for mixed workload testing
// Start to watch the configmaps | ||
watches := make([]watch.Interface, 0) | ||
var wg sync.WaitGroup | ||
for i := 0; i < total; i++ { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this supposed to simulate cilium's use case? In Cilium's use case, each pod is watched by each cilium agent, so it creates multiple watch updates for one mutation of a pod.
|
||
return &internaltypes.BenchmarkReport{ | ||
Description: fmt.Sprintf(` | ||
Environment: Combine %d read requests and %d update requests during benchmarking. Workload: Deploy %d configmaps in %d KiB`, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to measure anything of the watches?
Add read_update benchmark command for mixed workload testing and implement concurrent watch connections for all generated ConfigMaps.
Load Profile
Includes staleList (read) and Patch (update) operations.
Controlled via the --read-ratio flag to adjust the proportion of read vs. update actions.